Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | See parent post | Go Back
View Post [edit]

Poster: Administrator, Curator, or StaffJonathan Aizen Date: Oct 6, 2002 1:50am
Forum: etree Subject: Re: txt files

The reason these problems arise is because the text files are created in different operating systems which each have different characters to indicate the end of a line. MS notepad is particularly bad at reading files not created in Windows. I've had good success viewing files in IE. If a file shows up messed up in Notepad, I usually just view the file in IE, and copy and paste it into Notepad. Another great program that will convert Mac, DOS, and Unix formatted text files is called UltraEdit.

Reply to this post
Reply [edit]

Poster: Jay Date: Oct 6, 2002 2:04am
Forum: etree Subject: Re: txt files

Another really easy solution to this problem for PC users is to open the TXT file in Wordpad. Wordpad will display the file properly. Afterwards, you can just save it as a standard .TXT file, which will allow Notepad to read it if that's your viewer of choice.

I do this all the time, and it literally takes 2 seconds to open the file and resave it.

This post was modified by Jay on 2002-10-06 09:04:35

Reply to this post
Reply [edit]

Poster: gracek Date: Oct 6, 2002 4:55am
Forum: etree Subject: Re: txt files

Thanks for the heads up!

Reply to this post
Reply [edit]

Poster: raven Date: Oct 6, 2002 10:22am
Forum: etree Subject: Re: txt files

the only program i use to read the txt files is wordpad and i haven't had a single file look normal yet. no big deal though. i just thought that maybe i was doing something wrong or it was an easy fix. thanks for helping out though.

Terms of Use (10 Mar 2001)